Issues

MIDImage

Known Issues

Here there be Tygers...

IMPORTANT: This error has only been seen once, on one machine, but we feel it important enough to mention: MIDImage did not save the Settings file correctly. It renamed the existing Settings file to .bak, but did not save the new one...and gave no error. If you find a .bak file with no corresponding .lmpc file, just delete the .bak extension, reload, and try to save the Settings file or Project again. The most obvious indication that this error has occured will either be A) only the first Track is set when reloading the Project, or B) pressing the Preset button on the Image results in a distorted image.
MIDI files may not play at the correct tempo when loaded, but rather at the tempo of the last MIDI file to be loaded. This occurs both when a Project is loaded and when an individual MIDI file is loaded. After a pixel scan, the MIDI file does play correctly, however, and the file will play correctly when loaded in other MIDI players/editors.
When changing the position via the Go to Position menu or by clicking the MBT fields, the MIDI file plays at a very high speed until it reaches the new position. In some instances, after reaching the new file position, it will not play at all. (This will usually occur when the position is changed on a file which hasn't played yet, i.e. attempting to start at other than the beginning without first letting the file play normally.)
Some features of MIDImage need to be of a certain size. If you use Large Fonts or any custom size fonts (rather than the default Small Fonts) those features will look "wrong", but the program will still function as intended.
Very occasionally, a Velocity, Pan, or Mod Map may cause an access violation during track generation (the Track will be indicated by the "Notes so far" progress form). Clear the offending Map and the Map before it, and recreate them. If that does not take care of the problem, clear all the Maps and recreate them.